DEMview and its accompanying documentation are Copyright ⌐ 1995 by Ken Badertscher. All rights reserved.
Contents:
What is it?
What do I do with it?
For openers╔
DEMview Windows
DEM Files
All things being equal...
Error Alerts
What About Bryce?
Bryce DEM Images
Back to DEMview: What Doesn╒t Work
Sources for DEM Data
DEMview License
What is it?
DEMview is a US Geological Survey Digital Elevation Model file viewer. With it, you can view USGS digitized terrain data files, zoom and scroll around in them, and save them as 8 bit gray scale pictures. I wrote DEMview specifically to help me import real terrain files into KPT Bryce.
DEMview 1.0, including its documentation (collectively, ╥the Software╙), is free. It╒s not ╥free software╙ in the Free Software Foundation sense (sorry, rms), nor is it public domain. For details of what this means, see the DEMview License at the end of this document. In short:
Ñ You have permission to give the Software to others as long as you don╒t charge them for it.
Ñ Because the Software is provided free of charge, it comes with absolutely no warranty.
Ñ Because the Software contains copyrighted material, trade secrets and other proprietary material, you may not take the Software apart or create derivative works based on the Software in whole or in part.
In other words, please don╒t take credit for my work, don╒t profit by my work without my consent, and don╒t sue me for any reason, or I╒ll tell your mother.
What do I do with it?
First, you╒ll probably need to free up some disk space. Each uncompressed file of 1:250,000 scale digitized terrain data takes up about 9 megabytes. The 1201 by 1201 pictures generated by DEMview from those terrains consume about 1.3 MB. When you import those pictures into Bryce terrains at full scale, they take even more space. Also, these images consume a lot of memory. The minimum partition for DEMview (4 Mb) will barely hold a single 1í DEM file, and you probably won╒t be able to save the DEM image if you have that little memory (that╒s why I set the default size to 10Mb). Before you start playing, make sure you have plenty of disk and memory to play with.
Next, you╒ll need to get some DEM terrain files. These data files are distributed by the US Geological Survey and other organizations. You can get them direct from the USGS EROS Data Center either on the World Wide Web or by FTP. DEM files are also available on other FTP sites (see Sources for DEM Data). Most sites compress these files using the unix gzip utility, so you╒ll need either Stuffit Deluxe 3.5 or Mac Gzip to uncompress the files.
Once you have some uncompressed DEM files, you╒re ready to use DEMview.
For openers╔
Run DEMview. Select ╥Open╔╙ from the file menu. Pick a DEM file. DEMview will only open TEXT type files, so drop your DEM files on the ╥DEMview AutoTyper╙ if no files appear when you think they should (see What Works for more info). Wait about a minute, less if you have a speedy internal hard drive on a speedy Macintosh. While you wait, DEMview entertains you with an informative progress display:
╩
(If you don╒t have enough memory, you might see an alert box that tells you DEMview can╒t read the file.) Assuming you have enough memory, you╒ll presently see the DEM image displayed in 8-bit gray scale. Select ╥Save╔╙ from the file menu. Give it a clever name and hit the Save button. Congratulations, you have just mastered DEMview! Well, almost╔
DEMview Windows
Perhaps you╒re wondering ╥What╒s all that business in the DEMview windows?╙ Well, I╒ll tell you. In the upper left part of the window are two numbers separated by a gray ramp. These numbers indicate the minimum and maximum elevations in the terrain. For 1í DEM files, the ground coordinates (longitude and latitude) of the terrain boundaries are displayed in the lower left and upper right corners of the window. The ground coordinate display isn╒t always precise, so don╒t go planning any hiking trips based on the numbers there. The buttons at the lower left edge of the window allow you to zoom the view in or out. You can also scroll the DEM window using the arrow keys and page up/down, and zoom in or out using the + and - keys. The window title displays the current zoom level.
╩
UI notes:
Ñ Zoom buttons don╒t disable themselves when you can╒t zoom the view (but the View menu items do). DEMview won╒t let you zoom out so far that the window parts would run into each other, and it won╒t let you zoom in closer than 8:1 magnification.
Ñ If you╒re viewing a 1í DEM file, you╒ll notice that the ground coordinates have a lot of space around them. This is because I left room to display degrees, minutes and seconds. Other DEM files (like 7.5-minute files) lie on fractional degree boundaries.
Ñ Currently, there╒s no indication of units for the min and max elevations.
Ñ If you╒re viewing a 7.5-minute DEM file, you may notice 1-pixel wide strips along the edge of the image. This is not a bug in DEMview: 7.5-minute DEM files don╒t overlap map ╥neatlines,╙ and sometimes the neatlines don╒t fall on straight line boundaries. Because of this, some DEM files have irregular edges. If you piece together groups of these files, you╒ll notice that adjacent maps interlock with each other, sorta like a humongous jigsaw puzzle.
DEMview windows also allow you to define a Bryce-sized terrain selection to help prepare DEM images for Bryce input. If you drag in the DEM window, you can define a square selection of 64, 128, 256, 512 or 1024 elevations, if the DEM image is large enough. DEMview won╒t let you drag a selection that would fall outside the bounds of the DEM image, so if no selection rectangle appears, make sure you╒re dragging the mouse towards a part of the image that╒s big enough to contain a Bryce terrain. An indicator in the upper left corner of the window shows how big the current selection is.
╩
After you╒ve defined a selection, you can drag the selection with the mouse to cover a different part of the terrain. When the mouse cursor is over the selection, it changes to a right-pointing arrow. Just click anywhere in the selection rectangle and drag it around the DEM image. You can only drag a selection if part of its border is visible in the DEMview window (in fact, it╒s easiest if the entire selection is visible in the window). If you╒ve zoomed in to the middle of a selection so the selection borders aren╒t visible, the mouse will look like a grayed-out right-pointing arrow Zoom out or scroll the window until the selection rectangle is visible, and you╒ll be able to move it.
╩
DEM Files
USGS Digital Elevation Model files are specially formatted text files containing arrays of elevations for ground positions. Don╒t try to open a DEM file in a text editor, though! Though they are text files, they are typically distributed without record separators, so your text editor won╒t be able to read them. For the terminally curious, here╒s an example of what the start of a DEM file looks like:
MANNBORO,VA Free form information field ------------|Blank Filler field -----------------------------------|
NOTE: the terrain renderer Vistapro also uses ╥DEM╙ files, but the file format used by Vistapro is a proprietary binary format, different from the USGS standard text format. DEMview can╒t read Vistapro DEMs, only USGS DEMs.
DEM files come in several different flavors, typically referred to by the geographic dimension of the DEM. They are also sometimes referred to by the scale. The USGS makes ╥1-degree╙ DEMs (1:250,000 scale) freely available (see Sources for DEM Data). Most of these DEMs contain 1201 arrays of 1201 samples, spaced approximately 90 meters apart. A 1-degree DEM is about 108km on a side, with each sample covering approximately 2 acres. Higher and lower resolution DEMs are also available. The Rocky Mountain DEMs that come with DEMview are 7.5-minute DEMs. Each sample in a 7.5-minute DEM is 30 meters, or about 1/5 acre╤much finer detail than the 1-degree DEMs provide.
DEMview doesn╒t resample or interpolate DEM data, it only scales it to 256 gray levels. Many DEM files have an elevation range of thousands of meters, so you do lose some resolution when converting from DEM format to a gray scale image. That╒s also why, when importing DEM files into KPT Bryce, you need to scale the width and depth to match the reduction in scale caused by mapping DEM elevations to 256 gray levels. See ╥What About Bryce?╙ for the gory details.
DEMview will only open TEXT files. When you transfer a DEM file and unzip it, or copy one from a USGS CD-ROM, the file type won╒t be set properly for DEMview to open it automatically. I╒ve included an AutoTyper which will convert files for you:
╩
IMPORTANT NOTE: The DEMview AutoTyper will change ANY file into a DEMview text file. DO NOT drop applications or non-DEM data files on the DEMview AutoTyper, or you will render them inoperative.
As you might imagine, converting nine megabytes worth of raw terrain data into a picture takes a little bit of time. While DEMview is reading your file, it displays a floating window with the elapsed time and estimated time remaining. DEMview typically takes about 30 seconds to convert a 1í DEM file on my Quadra 800 (i.e., it slurps DEM data at a rate of about 328 KB per second). It tries to be nice when you put it in the background, in case you╒re really, really busy.
After opening a DEM file, you can save it as a PICT image. DEMview saves PICT files with the creator ╘8BIM╒, so you can open them in Photoshop for cropping and merging with other DEM images. If you have defined a selection before saving, DEMview will save only the selection. After it saves the selection, it tells you how much you╒ll need to scale it in Bryce so that it looks right.
All things being equal...
In case you didn╒t notice yet, DEMview sports a View menu, too. It provides menu items & key shortcuts for zooming, and an ╥Equalize╙ function The Equalize function is handy for piecing together multiple DEM files to create vast Bryce terrains. The way it works is: if you have more than one DEM file loaded, and you select ╥Equalize╙, all open DEM images are scaled to the combined minimum and maximum altitude. If you load more DEM files, they will be equalized as well. This will cause a loss of resolution, since you╒re trying to map more altitudes to the same 256 gray levels, but until DEMview can merge DEM╒s, the Equalize function helps. When you turn off Equalize, the open DEM images are restored to their original gray scale.
Error Alerts
DEMview will sometimes display alert boxes with cryptic error messages about exceptions being thrown in certain files. Sometimes it will display several of these in a row, before you see the ╥real╙ error alert. I╒ve tried to find all the cases where these alerts appear, but I may have missed a few. If you see a series of error alerts which are not followed by a user-level alert (something like ╥Unable to read Punxsatawnee.dem╙), or if you see an alert that says ╥Exception caught in LApplication╔╙ please let me know. It means that I╒ve screwed up the error handling somehow. You shouldn╒t have to deal with cryptic error messages, that╒s my job. If you report one, I╒ll send you a cool DEM.
What About Bryce?
This section was more important for primordial versions of DEMview, before it computed Bryce scaling values for you. I╒ve left it in in case you╒re interested in how it works╔
Converting DEM data into gray scale images is only the first step in rendering digitized Earth terrain in Bryce (well, maybe the first three steps). If you want to preserve the scale of the DEM data, you need to do a bit of work in and out of Bryce to get it right. You need to scale and position the terrains in Bryce so that they line up properly and all have the same relative scale. Soon, DEMview will be even more helpful in this respect, but for now, let╒s chew on some formulas.
Before you decide it╒s time to break out the old toothbrush and get to that grout cleaning you╒ve been putting off, let me reassure you: this isn╒t quite as nasty as it looks. Several of the above values are constants. You can get decent-looking terrains with a scale value of 1. You can approximate the horizontal resolution of 1:250,000 scale DEM files at 75 meters per profile (or meters per pixel in the image file). As near as I can figure, a Bryce ╥unit╙ sized object is about 200 camera units in size. So what you end up with is:
The pixel range depends on the size of the images you╒re importing for Bryce terrains (256, 512, 1024, whatever), and the meter range depends on the DEM file. DEMview displays the minimum and maximum altitude, so you can figure out the range from those numbers. This stuff is easiest to work with in a spreadsheet if you╒re trying to compose a Bryce terrain from multiple DEM images. Here╒s an example of one I worked with when putting together the Grand Canyon:
╩
The only thing I had to enter in the spreadsheet were the quad names and the ╥DEM Zmin╙ and ╥DEM Zmax╙ values. The formulas did the rest.
Yeah, that╒s real neat and all, but what about Bryce?
Okay, you got me. All you really have to do is save the DEM files as Bryce terrains, and line them up next to each other in Bryce. That╒s it! Really! If you want to make a truly huge terrain out of lots of different DEM quads, load them all up into DEMview, and use the Equalize menu item to set them all to the same gray level. Save them as image files, keeping a note of the scale value DEMview tells you, and paste them together with an image editing program. This is presently the best way to piece together 7.5-minute DEM files, since they have irregular edges. It╒s much easier to preassemble them in a drawing program than to line them up in Bryce.
If you just can╒t stand the resolution loss caused by the ╥Equalize╙ function, or you really enjoy spending time lining up terrains in Bryce, you can do it the old way:
After using DEMview to convert the terrain data to gray scale images for Bryce, and creating the actual Bryce terrains, make them all unit-sized, center them in Bryce space, and display them as boxes (not mesh). For each terrain, do the following:
1) Position the camera horizontally at one half of the ╥Bryce XZ╙ coordinate listed above, in the X direction, and aim it straight down the Z axis (using Bryce╒s ╥Front╙ view, perhaps). Scale the terrain in the X direction so that the box edge lines up straight in the direction the camera is looking.
2) Repeat step 1 to scale the Z size while looking down the X axis (the ╥Side╙ view).
3) Position the camera at the vertical ╥Bryce Y╙ coordinate, and scale the terrain vertically so that it lines up with the camera.
4) Move the camera up ╥Bryce ╞Y╙ units (I believe more negative values increase upward, but it╒s been a while since I actually did this), and hit option-page-up ╥Bryce ╞Y╙ times. The terrain should be aligned with the camera.
5) Position the terrain horizontally so that the correct corner is centered in Bryce space.
Pick a spiffy material for the terrains, and you╒re off.
Perhaps now you have some idea of what inspired me to write DEMview.
Bryce DEM Images
There some other things to consider when rendering DEM terrains in Bryce. If you want it to look realistic, you don╒t want to get too close to the terrain. The horizontal resolution of 1í DEM files is between 60 and 90 meters per pixel in the DEM image. Like any other smoothed terrain in Bryce, if you get too close to DEM terrains, they start to look blobby. Blobbiness is not a characteristic of most Earth terrain.
On the other hand, the horizontal-to-vertical scale ratio of DEM files is very different from other KPT Bryce terrains. You don╒t want to get too far from the terrain, or it will look flat. You won╒t get looming mountains and dramatic canyons if your camera is a dozen kilometers up in the air. Keep in mind that 1-degree DEMs are 108km on a side, and typically only 1-2km tall. That╒s why DEM terrains look flatter from a distance... even a few hundred camera units away from the terrain is several kilometers up. Bryce-generated terrains operate on a much smaller scale.
Often, interesting terrain features lie on the boundaries of USGS quadrangles. To render these, you have to go through that complicated process of lining up and scaling all the terrains just right. I have found it very difficult to get seamless alignment of terrains scaled with different gray levels. You can usually fudge it with patch boxes or cylinders, but it╒s best to match up the images in Photoshop. An unfortunate side-effect is that you lose vertical resolution. I have toyed with 24-bit color ramps that provide better than 256 gray levels, based on ITU standard gray scale computation. That would at least let you manipulate the images in Photoshop without losing resolution. The next version of DEMview will allow you to merge multiple DEM files into a single Bryce terrain.
Zeroing in on interesting terrain features can be a challenge, too. What I do is create marker objects (cylinders or pyramids) and give them an obnoxious color. I scale them down really tiny, and put them at interesting places in the terrain using the top, side and front views. Then I aim the camera at the marker by directly manipulating the blue camera line (in the top, side and front views). When I go back to the main view, I tweak the camera position as needed. When I get it just right, I move the marker object beneath the terrain, and render away.
╩
Back to DEMview: What Doesn╒t Work
That circular symbol is a ╥logic hazard╙, similar in concept to biohazard or nuclear waste symbols, but for software. Landon Dyer dreamt that one up, way back when he worked for Atari.
DEMview requires System 7, but does not check to see if any of the features it uses are available.
DEMview uses temporary memory for some of its permanent data structures (this memory shows up as used by ╥System Software╙ in the ╥About This Macintosh╙ Finder window). This is left over from early debugging phases, where I didn╒t want to worry about giving DEMview enough memory.
I haven╒t determined a good ╥suggested memory size╙ for DEMview. It isn╒t particularly friendly about low memory conditions, but it isn╒t nasty either. It should politely fail to do things if it runs out of memory.
DEMview doesn╒t distinguish between low memory errors and file read errors when trying to open a file.
I╒ve left exception alerts on. If something goes wrong, you╒re liable to see one or more alerts about exceptions being thrown before you see the actual error alert.
╩
Sources for DEM Data
Note: these sites are active as of this writing (95-05-30), but WWW pages and FTP servers come and go. No warranty is expressed or implied. I╒ve also heard rumors (on NPR) that Congressional budget slashing may affect the USGS. It would be a major drag if all this government-collected data were privatized. Fight for your right to render: write your Congressman!
The USGS Geo Data home page is at http://sun1.cr.usgs.gov/doc/edchome/ndcdb/ndcdb.html. Terrain data for the entire US is available via FTP from the server edcftp.cr.usgs.gov in the directory /pub/data/DEM/250/. Files there are organized alphabetically by USGS quadrangle name. Unless you have a dictionary of USGS quadrangle names in your head, you╒ll probably prefer the WWW site. It has a list of quads by state, and a nifty graphical browser that lets you zoom from a map of the US down to individual quads.
The USGS is also working on publishing 30-degree (1:1,000,000 scale, or about 1km per sample) data for the entire world. Data sets for Africa, Japan, Madagascar and Haiti are currently available from the aforementioned FTP server in the directory /pub/data/30ASCWDEM. (Disclaimer: I have not yet tried reading 30-degree DEM files with DEMview). The data is also available on CD-ROM from the USGS (see their WWW home page for more information).
Another interesting FTP site is the ╥Spectrum Swap Meet╙. A server at Xerox, spectrum.xerox.com, has a wealth of information on digitized terrain. Lots of smaller scale (7.5 minute scale, or 30m horizontal resolution) digitized terrain is available there, as well as copies of some of the more interesting USGS data sets and sample images. The ╥doc╙ directory contains fax-compressed TIF files which comprise the USGS publication ╥Data Users Guide 5 - Digital Elevation Models╙. Sure, it╒s only a buck if you order it from the USGS, but what the heck, right? The URL for the Spectrum Swap Meet is ftp://spectrum.xerox.com/pub/map/dem.
Brandon Plewe has a page on the web which lists a number of U.S. geographic data archives. It╒s at
http://wings.buffalo.edu/geoweb/sources.html.
I╒m also told that a whole lotta USGS DEM files are included on the Vista Pro CD-ROM. And of course, some are available on the CD-ROM that comes with the KPT Bryce book!
An Unsolicited Plug
If you╒ve read this far: good for you! Here╒s your cookie:
╩
If you don╒t have this utility, GET IT NOW! You╒ll find it much easier to peruse SimpleText documents like this one with the cool menu SimpleText Color Menu adds to SimpleText:
╩
DEMview License
1. License. The application software and documentation accompanying this License, whether on disk, in read only memory, or on any other media (the ╥Software╙) are licensed to you by Ken Badertscher (the ╥Author╙). You own the media on which the Software is stored, but the Author and/or the Author╒s Licensor retain title to the Software. This License allows you to use the software and to give copies of the Software to a third party, provided that:
a) the Software is redistributed unchanged, in the same form as you received it, and
b) you redistribute the Software free of charge, and
c) the third party reads and agrees to accept the terms and conditions of this License
2. Restrictions. The Software contains copyrighted material, trade secrets and other proprietary material. In order to protect them, and except as permitted by applicable legislation, you may not decompile, reverse engineer, disassemble or otherwise reduce the Software to a human-perceivable form. You may not modify, rent, lease, loan or create derivative works based upon the Software in whole or in part.
3. Redistribution. You are permitted to redistribue the software free of charge. You may not charge more than the cost of the distribution medium for redistributing the software. This restriction includes computer Bulletin Board Systems which maintain ╥download ratios╙╤ if you make the Software available on such a system, allow users to transfer the Software without charging them for time or bytes transferred.
3. Termination. This License is effective until terminated. You may terminate this License at any time by destroying the Software and all copies thereof. This License will terminate immediately without notice from the Author if you fail to comply with any provision of this License. Upon termination, you must destroy the Software and all copies thereof.
5. Export Law Assurances. You agree and certify that neither the Software, nor any other technical data received from the Author, nor the direct product thereof, will be exported outside the United States except as authorized and permitted by the laws and regulations of the United States. If the Software has been rightfully obtained by you outside the United States, you agree that you will not reexport the Software nor any other technical data received from the Author, nor the direct product thereof, except as permitted by the laws and regulations of the United States and the laws and regulations of the jurisdiction in which you obtained the Software.
6. Government End Users. If you are acquiring the Software on behalf of any unit or agency of the United States Government, the following provisions apply. The Government agrees: (i) if the Software is supplied to the Department of Defense (DoD), the Software is classified as "Commercial Computer Software" and the Government is acquiring only "restricted rights" in the Software, its documentation and fonts as that term is defined in Clause 252.227-7013(c)(1) of the DFARS; and (ii) if the Software is supplied to any unit or agency of the United States Government other than DoD, the Government╒s rights in the Software, its documentation and fonts will be as defined in Clause 52.227-19(c)(2) of the FAR or, in the case of NASA, in Clause 18-52.227-86(d) of the NASA Supplement to the FAR.
7. NO WARRANTY. You expressly acknowledge and agree that use of the Software is at your sole risk. Because the Software is provided free of charge, the Author provides no warranty for the program, to the extent permitted by applicable law. Except when otherwise stated in writing, the Author provides the Software ╥as is╙ without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement. The entire risk as to the quality and performance of the program is with you. Should the program prove defective, you assume the cost of all necessary servicing, repair or correction.
As required by the Metrowerks licensing agreement:
The Author and the Author╒s licensors EXPRESSLY DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE AUTHOR AND THE AUTHOR╒S LICENSORS DO NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET YOUR REQUIREMENTS, OR THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. FURTHERMORE, THE AUTHOR AND THE AUTHOR╒S LICENSORS DO NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF THE SOFTWARE IN TERMS OF THEIR CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY THE AUTHOR, THE AUTHOR╒S LICENSORS OR AN AUTHOR AUTHORIZED REPRESENTATIVE SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU (AND NOT THE AUTHOR OR AN AUTHOR AUTHORIZED REPRESENTATIVE) ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU.
8. Limitation of Liability. Under no circumstances, including negligence, unless required by applicable law or agreed to in writing will the Author or the Author╒s licensors be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use the program (including, but not limited to, loss of data, or data being rendered inaccurate, or losses sustained by you or third parties, or a failure of the program to operate with any other programs), even if the Author an Author authorized representative have been advised of the possibility of such damages.
In no event shall the Author or the Author╒s licensors total liability to you for all damages, losses and causes of action (whether in contract, tort (including negligence) or otherwise) exceed that portion of the amount paid by you which is fairly attributable to the Software.
10. Controlling Law and Severability. This License shall be governed by and construed in accordance with the laws of the United States and the State of California, as applied to agreements entered into and to be performed entirely within California between California residents. If for any reason a court of competent jurisdiction finds any provision of this License, or portion thereof, to be unenforceable, that provision of the License shall be enforced to the maximum extent permissible so as to effect the intent of the parties, and the remainder of this License shall continue in full force and effect.
11. Complete Agreement. This License constitutes the entire agreement between the parties with respect to the use of the Software, and supersedes all prior or contemporaneous understandings or agreements, written or oral, regarding such subject matter. No amendment to or modification of this License will be binding unless in writing and signed by a duly authorized representative of the Author.
By running the program, you indicate acceptance of these terms.
If you have any questions or comments concerning this License, please do not hesitate to contact the Author via electronic mail at KenBad@aol.com.
May 30, 1995
Ken Badertscher (KenBad@aol.com)
This document was created using ClarisWorks¿ 3.0 by Claris, exported to SimpleText format using Alan Coopersmith╒s TeachText & SimpleText XTND Translator 2.0. Screen shots were captured using FlashIt¬ 3.0 by Nobu Toge.
